Irrigation controller and system integrating no-watering restrictions and an empirically-derived evapotranspiration local characteristic curve

ABSTRACT

A convenient, water-saving and labor-saving FROG irrigation controller and system are provided, which determine the appropriate water budget and schedule for the property&#39;s landscaping based on evapotranspiration data for the geographic area, regulation data (any mandated and voluntary watering restrictions), and property-specific data, with consideration given to reduction in watering days, increase in soil watering depth, and day of year. Once set, the FROG controller provides incremental adjustments over the course of the year; the homeowner no longer needs to re-set the watering program seasonally to comply with local mandated and voluntary watering restrictions. Compliance is automatic and obligatory, meeting the water saving goals of the local water authority. Optionally presented is a web-based wizard used to determine a customized water budget/schedule that is input into the FROG controller through a data storage unit or wireless input.

CROSS-REFERENCE TO RELATED APPLICATION

This continuation application claims the benefit of co-pending U.S.patent application Ser. No. 14/030,067 filed on Sep. 18, 2013, which isa division of U.S. patent application Ser. No. 13/080,201 filed on Apr.5, 2011 and now U.S. Pat. No. 8,565,904, which was acontinuation-in-part application claiming the benefit of U.S. patentapplication Ser. No. 12/755,337, filed on Apr. 6, 2010, which areincorporated herein in their entirety. PCT Patent Application No.WO2010/118053, filed on Apr. 6, 2010, is a related application.

FIELD OF THE INVENTION

The present invention relates generally to an irrigation control system,and more particularly, to a controller (add-on or standalone)configurable using an empirically-derived evapotranspiration localcharacteristic curve and local mandatory and voluntary no-wateringrestrictions.

BACKGROUND INFORMATION

Irrigation controllers are commonly known in the prior art. They areelectromechanical devices that control water delivery to a plurality ofzones through the programmed opening and closing of water controlvalves, such as solenoid valves. For example, a residential landscapemay be divided into eight separate watering zones. Some of the zonesencompass turf requiring relatively more water delivered throughsprayers. Some of the zones encompass bushes and trees requiringrelatively less water delivered through bubblers and drip emitters.Homeowners or landscapers program the irrigation controller to deliverdifferent amounts of water to these different zones by varying theamount of time the water control valves remain open in the course of agiven irrigation cycle. For example, the valve covering Zone 1, a turfzone, may be programmed to be open five days per week (“watering days”),three times per day at specific times of the day (“start time”) for tenminutes (“run-time duration”); the valve covering Zone 2, a bush andtree zone, may be programmed to be open only three days per week, threetimes per day immediately following the cycles of Zone 1, but withrun-time durations of only five minutes; and so on and so forth.

A limitation of such existing irrigation controllers is that they mustbe manually reprogrammed to respond to seasonal changes, as well as towatering restrictions mandated by local water authorities (“mandatedwatering restrictions”). Ten minutes of water, three times per day maybe appropriate for a turf zone in summer, but excessive for winter.Moreover, in summer, the irrigation controller may be programmed towater on any day of the week, but in winter, mandated wateringrestrictions may limit “allowed watering days” to just one day per week,with six days a week mandated as “mandated no watering days.” To effectthe changes needed to adjust for the seasons and mandated wateringrestrictions, homeowners and landscapers must manually reprogram thecontroller.

Because the foregoing changes are few in number—typically four times peryear corresponding to the four seasons—and because conventionalirrigation controllers are relatively easy to reprogram, implementingthe required seasonal changes and mandated watering restrictions shouldbe an acceptable burden. However, even if homeowners and landscapersfaithfully reprogram their irrigation controllers these four times peryear, this would still result in a substantial amount of water waste.Moreover, local water authorities find that their water conservationprograms are far less effective than they should be due to the failureof homeowners and landscapers to comply with mandated wateringrestrictions, because even the few and simple steps needed to complywith them are too difficult for many homeowners and landscapers, or theysimply do not implement them.

The water waste inherent in four-times-per-year reprogramming ofconventional irrigation controllers is caused by the fact that the waterdemand of plants changes far more frequently than just four times peryear. The water demand of plants is dictated by the rate at which plantslose moisture to evaporation, and the rate at which they are capable ofreplacing it (“evapotranspiration”). Evapotranspiration is influenced bymany factors, including temperature, humidity, soil moisture, soil type,sun exposure, wind, type/amount of mulch, and, of course, plant type.

Some factors, such as plant type and sun exposure, are taken intoaccount through the regular programming of a conventional irrigationcontroller. For example, a homeowner knows he has trees and shrubs, notturf, in Zone 2 of his yard, and that this portion of the yard is shadedfrom the sun. He takes this into account by watering Zone 2 withbubblers and drip emitters, rather than the sprayers used on turf zones.He also takes it into account by programming his conventional irrigationcontroller with start times and run-time durations that make sense forthis plant type and for shade conditions (as well as soil type and otherfactors).

However, the homeowner cannot take evapotranspiration factors intoaccount in this way. For example, temperature, humidity and windfluctuate constantly, changing the water demand of plants constantly—andfar more often than four times per year. Reprogramming an irrigationcontroller four times per year takes into account a range of thesefluctuations. For example, in summer, temperatures in the Las VegasValley typically range between 80° F. and 115° F., versus winter whenthey may range between 35° F. and 65° F. The fact is, however, thatthese ranges are very broad. For example, an irrigation controllerprogrammed to deliver water in accordance with the average anticipatedtemperature in the middle of the range may result in plant loss duringhot, dry spells in midsummer, yet may deliver more water than isnecessary at the beginning and end of the summer season. Thus, thecurrent situation is detrimental to both homeowners (less than optimalwater delivery) and the water authority (extra water use early and latein season).

With regard to mandated watering restrictions, some non-compliance isdue to unwillingness of homeowners and landscapers to obey them.However, most non-compliance, according to local water authorities, isdue to indifference or ignorance of the mandated watering days, despitelocal water authorities' best efforts to publicize them, or is due toconfusion over when and where they apply. For example, differentsections of a local water authority's jurisdiction may be assigned awatering group, such as “A” or “B.” Homeowners in “A” may be assignedthe allowed watering days Monday, Wednesday and Friday. Homeowners in“B” may be assigned the allowed watering days Tuesday, Thursday andSaturday. Thus, a homeowner must know whether he is in assigned wateringgroup “A” or “B,” and must additionally know the allowed watering daysfor that watering group—all of which changes four times per year. Assimple as this may seem, it is apparently too much for a substantialpercentage of homeowners and, to the extent homeowners rely on them,landscapers.

Industry has responded to the foregoing problems by creating what areknown as “smart controllers.” Following are examples of differentapproaches taken by smart controller developers.

One approach has been to make irrigation more scientific by benefitingfrom academic research on evapotranspiration. U.S. Pat. No. 5,208,855issued to Marian discloses a smart controller outfitted with a receiverto pick up evapotranspiration data broadcast by weather stations andagricultural extensions. Such broadcasts consist of daily informationfor various localities about environmental factors such as temperature,humidity and wind. These data have been processed to determine theireffect on evapotranspiration and, thus, water need for a reference crop,generally turf (determining what is known as referenceevapotranspiration or “ETo”). Upon setting up the Marian smartcontroller, the user inputs locality and information about the type ofplants he is irrigating, so that the smart controller may automaticallypick up the broadcast ETo information corresponding to the user'slocality, and calculate the water need of the user's plant matter as apercentage of ETo (based upon crop coefficients, which are publishedanalyses of the evapotranspiration water needs of plant types as apercentage of the evapotranspiration water needs of the reference crop).Unfortunately, Marian's smart controller has numerous drawbacks for theaverage homeowner: (1) its emphasis on crop coefficients is suited toagriculture, not average homeowners, (2) the need for a receiver andrelatively complicated data entry screen contribute to cost andcomplexity, and (3) the need for the homeowner to reset his irrigationcontroller seasonally is not removed. In the case of agriculture, thesedrawbacks are less important, because farmers are willing to, and dodevote great attention to irrigation systems. Average homeowners do not,and a disruption to irrigation, for example, could subsist for daysbefore a homeowner even noticed it. Additionally, Marian's smartcontroller does not facilitate the water authority's goal of increasedcompliance with mandatory watering restrictions.

U.S. Pat. No. 6,453,216 issued to McCabe et al. and U.S. Pat. No.6,892,113 issued to Addink et al. disclose devices using historicalevapotranspiration data as the means to determine a watering budget(McCabe et al.) or as part of the means to do so (Addink et al.). Forexample, historical evapotranspiration data may consist of an average ofthe evapotranspiration data for the same date over a multiyear period,e.g., December 1, for a specific location, e.g., Amarillo, Tex., for thethree years 2000, 2001 and 2002. The advantage of using historicalevapotranspiration data is that they free the user from needing toobtain current data, for example, by broadcast transmission, andentering current data into the smart controller. Instead, the historicaldata can be preloaded into the smart controller, enabling the smartcontroller to deliver water in accordance with the average historicalevapotranspiration for that date and location. U.S. Pat. No. 6,314,340issued to Mecham et al. discloses a device that measures high and lowtemperatures for the day, and then uses a specific formula, namely, theHargreaves formula, to determine an appropriate watering budget.However, none of these patents address the problems of lack ofcompliance with mandated watering restrictions or with the troublesomerequirement for the homeowner to reset the irrigation schedule of hisirrigation controller each season to meet seasonal watering needs and/orseasonal mandated watering restrictions.

Another approach has been to create smart controllers capable oftracking one or more of the environmental factors affectingevapotranspiration rate, and increasing or decreasing water output inaccordance with them. For example, U.S. Pat. No. 4,684,920 issued toReiter and U.S. Pat. No. 4,922,433 issued to Mark focus on soilmoisture. Using sensors placed in the ground throughout the area to beirrigated, these smart controllers benefit from real-time soil moisturereadings in order to provide the right amount of irrigation. However,while these devices may be suitable for agricultural or commercial use(e.g., golf courses and shopping centers), they are not suitable foraverage homeowners, because the deployment and maintenance of soilsensors require too much effort and expense relative to homeowners'modest landscaping needs.

U.S. Pat. No. 6,892,114 issued to Addink et al., and U.S. Pat. No.7,165,730 issued to Clark disclose smart controllers capable ofmeasuring one or more environmental factors for the purpose of modifyingthe irrigation schedule of a conventional controller. However, bothdevices disclose suboptimal design, since they are not in series betweenan existing controller and the irrigation valves, but communicate onlywith the existing controller to modify an irrigation cycle, as discussedin greater detail below. U.S. Pat. No. 7,266,428 issued to Alexanianfocuses solely on temperature as the predominant environmental factoraffecting evaporation rate, and uses a non-standard evapotranspirationformula based solely on temperature to create water budgets.

U.S. Pat. No. 5,839,660 issued to Morgenstern et al. focuses primarilyon precipitation and wind, disclosing a smart controller that measuresthese environmental factors and cuts off irrigation if either oneexceeds a set value.

However, the smart controllers using environmental factors presented inthese patents do not increase compliance with mandated wateringrestrictions nor decrease the work for the homeowner in resetting theirrigation controller at least seasonally.

Yet another approach has been to provide smart controllers giving usersgreater control over their irrigation systems. For example, U.S. Pat.No. 7,010,396 issued to Ware et al. covers an irrigation controller withan embedded Web server enabling the user to interact remotely and,hence, more frequently and conveniently with the controller. However,for the average homeowner, what is needed is not more involvement withthe irrigation controller, but greater irrigation efficiency withoutmore involvement.

Further, when adjusting the watering run-time duration or cutting offthe irrigation, smart controllers of the prior art do not take intoconsideration the number of mandated no-watering days blocked out andthe additional increased reduction in water delivery. For instance, insome regions in winter, there is only one allowed watering day per week,with six days of the seven mandated as no-watering days. If theirrigation is cut off on the one allowed watering day (such as due to anenvironmental factor), no irrigation will be given for two weeks.Similarly, as described in U.S. Patent Publication No. 2010/0030476 byWoytowitz et al., on the one allowed watering day, the watering run-timeduration may be reduced by a relatively large percentage based onenvironmental factors through a seasonal adjust feature based onhistorical evapotranspiration rates, without accounting for theadditional reduction forced by the six mandated no-watering days.

Unfortunately, no prior art device has effectively solved the problem ofmaking irrigation efficiency more affordable and less burdensome for theaverage homeowner, while providing a simple means to implement localmandated watering restrictions, and thus promote the water-saving goalsof the local water authority by increasing compliance. Smartcontrollers' complexity and expense, as well as their suboptimal designand methodology, have prevented them from penetrating this market thatis crucial not only from a profit standpoint, but from a water andenergy conservation standpoint. (For example, pumping water to the LasVegas Valley is the region's single greatest use of energy.)

SUMMARY OF THE INVENTION

The present invention, referred to here as the FROG smart irrigationcontroller, is directed to an easy-to-use, labor-saving irrigationcontroller that controls the start time and run-time duration of theirrigation valves based on a FROG watering schedule derived by using aFROG integration of (1) “evapotranspiration data” (including an“ETo_local” factor—the value of the ETo characteristic curve for aparticular day in the particular geographic location—based on theempirically-derived evapotranspiration local characteristic curvesetting forth the water need of the locally predominant variety oflandscape material at different times of the year for the particulargeographic area), (2) “regulation data” (including mandated wateringrestrictions applicable to the location [such as no-watering days,restricted-watering hours, assigned watering group] and includingvoluntary restrictions [such as an extra donated no-watering dayincentivized by a water bill credit]), and (3) “property-specific data”(data relating to the specific landscape and watering system of theparticular property, such as plant type, property-specific plantenvironment [e.g., sun/shade conditions, mulch type and amount, terrain,and soil type], number of valves/zones, emitter types, etc.). An exampleof this FROG integration is provided in the novel FROG algorithm basedon total water volume, presented herein.

The FROG controller is presented herein as an add-on controller, as astandalone controller, and as an add-on controller convertible to astandalone controller; it can be initialized, updated, and/orreprogrammed using one or a combination of five presented methods ofloading data into the controller: a preloaded mode, a learn mode(embodiment one, FIG. 1), a manual control input mode (embodiment two,FIG. 2) data input mode (embodiment four, FIG. 4, and embodiment five,FIG. 13-16), and a wireless input mode (embodiment five, FIG. 13-16).Additionally, the third embodiment of FIG. 3 presents sensor inputs thatcan optionally be used in the FROG integration.

Five exemplary embodiments that use the FROG integration and/or FROGalgorithm of the current invention are presented. In the firstembodiment (FIG. 1), the FROG is a simple add-on device in seriesbetween a conventional irrigation controller (the “existing controller”)and irrigation valves. It receives property-specific data by utilizingthe learn mode. As shown in FIG. 14, the evapotranspiration data andregulation data may be preloaded into the system before distribution ofthe FROG controller, or may optionally be input into the FROG controllerby using the data storage input mode or wireless input mode of the fifthembodiment.

In the second embodiment (FIG. 2), the FROG is a comprehensive,standalone controller, allowing manual input of property-specific databy manipulation of the physical controls to set the start times andrun-time durations for the multiple zones, as well as operating theirrigation valves, negating the need for a conventional controller. Theevapotranspiration data and regulation data may be preloaded into thesystem before distribution of the FROG controller, or may optionally beinput into the FROG controller by using the data storage input mode orwireless input mode of the fifth embodiment.

In the third embodiment (FIG. 3, FIG. 4), the FROG controller (eitherthe add-on or standalone) receives sensor data from environmentalsensors, and the water budget algorithm additionally utilizes thesesensor data. The environmental sensors may be located within (“onboard”)or near the FROG housing, or may be in a freestanding remote weatherstation (as shown). The sensors may be directly connected or wirelesslyconnected to the FROG. The one or more environmental sensors may measuretemperature, humidity, solar radiation, rainfall, etc. When the sensorinformation is provided, the FROG algorithm is modified to additionallyuse the one or more received current environmental values, preferablyafter an environmental-factor averaging calculation is performed.

In the fourth embodiment (FIG. 5 to FIG. 7), a data input system isprovided, which may be utilized with any of the other presentedembodiments.

The fifth embodiment (FIG. 13 to FIG. 16) illustrates using an SD cardas a data storage unit. The fifth embodiment can optionally also beconfigured to utilize the wireless input mode using a standard wirelessnetwork to receive data.

Multiple methods of initializing, configuring and updating the FROG arepresented, including a learn mode, a manual control mode, a data storageunit input mode, and a wireless input mode. These modes can be usedalone or in combination. In the learn mode method, the FROGautomatically “learns” the programmed watering schedule (“initialwatering schedule”) including the start times (“initial start times”)and run-time durations (“initial run-time durations”) of the existingcontroller in a “learn mode.” In the manual control mode the homeownercan use physical buttons and dials to input data. (The term “homeowner”or FROG controller “user” can refer to the owner or renter of the home,the landscaper, the irrigation installer, a business owner, or otherperson authorized to install, update or re-program the FROG controller.)In the data storage unit input method and wireless input method, datacan be input through use of a data storage unit inserted into the FROGcontroller or wirelessly, either by the water authority or by the userafter accessing a website server and using a customization wizard toinput property-specific data. The user defines and characterizes theplant information (type, environment, terrain, amount of sun, etc.)along with the irrigation system information (number of valves, types ofemitters, etc.). The FROG water budget algorithm creates the waterbudget and schedule customized to meet the user's landscaping needs.This customized water budget and schedule is transferred to the FROGcontroller by use of a physical data storage unit or a wirelesstransmission; this may be either to initialize or to update the FROGcontroller. After initializing, the FROG takes over the scheduling ofirrigation and operation of the irrigation valves, implementing the FROGwatering schedule. The FROG controller then controls the valves of theirrigation system to implement the FROG customized water budget.

In another aspect, the FROG smart controller is also designed with auser-donated (and preferably user-selectable) “float” day, which is a“voluntary no-watering day.” In exchange for a credit applied to thehomeowner's water bill, the homeowner may designate one additional dayas a voluntary no-watering day. Thus the water saving goals of the waterauthority are furthered.

An object of the present invention is to provide a FROG smart controllerthat implements mandatory watering restrictions, thus insuringcompliance and saving water.

A further object of the present invention is to provide a FROG smartcontroller that is easy to operate and convenient for the user.

An additional object of the present invention is to provide a FROG smartcontroller that provides incremental adjustments of the water budget, asopposed to merely seasonal adjustments.

Another object of the present invention is to provide a FROG smartcontroller that delivers a customized water budget (the appropriateamount of water to meet the need of the landscape plants at differenttimes of the year for the particular property or location, while takinginto consideration local water authority regulations).

These and other objects, features, and advantages of the presentinvention will become more readily apparent from the attached drawingsand from the detailed description of the preferred embodiments, whichfollow.

BRIEF DESCRIPTION OF THE DRAWINGS

The preferred embodiments of the invention will hereinafter be describedin conjunction with the appended drawings, provided to illustrate andnot to limit the invention, where like designations denote likeelements, and in which:

FIG. 1A depicts a front view of the FROG add-on controller of the firstembodiment of the present invention having a graphic display and beingconnected to an existing conventional irrigation controller.

FIG. 1B depicts a front view of the FROG add-on controller of the firstembodiment of the present invention having a simplified user-interfacewithout a graphic display screen and being connected to an existingconventional irrigation controller.

FIG. 2 depicts a front view of the FROG standalone controller withmanual controls of the second embodiment of the present invention.

FIG. 3 depicts a front view of a sensor module attached to the FROGadd-on controller of the third embodiment of the present invention,wherein the FROG add-on controller is in communication with a weatherstation housing one or more environmental sensors and is connected to anexisting conventional irrigation controller.

FIG. 4 depicts a front view of a FROG standalone controller of thefourth embodiment of the present invention, wherein the FROGcomprehensive controller is in communication with one or moreenvironmental sensors.

FIG. 5A depicts a side view of the FROG controller of the fourthembodiment of the present invention configured with the data inputsystem embodied as a reader slot and optical reader.

FIG. 5B depicts a top view of the FROG controller of the fourthembodiment of the present invention configured with a data input systemembodied as a reader slot and optical reader.

FIG. 5C depicts a front view of an insertable sheet imprinted with a QRCode®-type optical code (such as could be printed on a customer's bill)for inserting into the reader slot of the data input system.

FIG. 5D depicts a detail of the circle of FIG. 5C showing the QRCode®-type optical code readable by the optical reader.

FIG. 6A depicts a side view of the FROG controller of the fourthembodiment of the present invention configured with the data inputsystem embodied as a slide slot and a magnetic strip reader.

FIG. 6B depicts a top view of the FROG controller of the fourthembodiment of the present invention configured with a data input systemembodied as a slide slot and a magnetic strip reader.

FIG. 6C depicts a front view of a card carrying a data-impregnatedmagnetic strip configured to slide through the slide slot to allowreading by the magnetic strip reader.

FIG. 7A depicts a side view of the FROG controller of the fourthembodiment of the present invention configured with a data input systemincluding a controller electronic connection for receiving a datastorage unit.

FIG. 7B depicts a top view of the FROG controller of the fourthembodiment of the present invention configured with the data inputsystem including a data storage unit-receiving controller electronicconnection.

FIG. 7C depicts a front view of a data storage unit, such as a USB flashdrive or the like, configured with a complementary electronicconnection.

FIG. 8 depicts a schematic of the add-on FROG smart controller of thefirst embodiment. The installed existing controller 20 is wiredzone-by-zone through bridge cable 12 to the main control unit of theFROG controller 10.

FIG. 9 depicts a schematic of the remote weather station 40 of the thirdembodiment.

FIG. 10 depicts the reference evapotranspiration curve (from whichETo_local for each time point is derived) of the type used by the FROGsmart controller to determine the correct watering needs of landscapematerial in a given geographic location, such as the Las Vegas Valley,for a given time of year.

FIG. 11 depicts a schematic of the variables of an exemplary FROGalgorithm of the FROG integration.

FIG. 12 depicts a flowchart of the learning mode method.

FIG. 13 depicts a perspective view of the FROG controller of the fifthembodiment of the present invention wherein the data input systemcomprises an SD card receiving slot.

FIG. 14 depicts methods of inputting data for the add-on, theconvertible, and the standalone FROG controller. The data that can beinput include: property-specific data, evapotranspiration data,regulation data (voluntary and water authority restrictions), and thecustomized water budget/schedule 105 for the homeowner's landscape.

FIG. 15 depicts an online configuration and customization wizardprovided to allow the homeowner to input property-specific data enablingthe FROG integration and/or algorithm to create a customized waterbudget/schedule 105 for the homeowner's landscape while implementingregulation data.

FIG. 16 depicts an exemplary mesh network usable in the wireless inputmode of the preferred fifth embodiment of the present invention.

Like reference numerals refer to like parts throughout the several viewsof the drawings.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Shown throughout the figures, the present invention is directed toward aFROG smart controller 10 that improves the efficiency of irrigationscheduling and saves water through use of a FROG integration ofevapotranspiration data and regulation data applied to property-specificdata. Consequently, the FROG controller 10 provides advantages for boththe homeowner (convenience, labor reduction, improved water deliverycorrelated to day of year) and the local water authority (obligatorycompliance with mandated watering restrictions). An important strategyin reaching the water saving goals of the local water authority is metthrough the hard-to-achieve increased compliance resulting from use ofthe FROG irrigation control system.

As opposed to the conventional automatic controllers for in-groundirrigation systems that the homeowner must reset four times a year tomeet the seasonal watering need changes and the seasonal changes inlocal water authority mandated watering restrictions, the homeownerinitially sets the FROG controller 10 and then forgets it, with nofurther effort required (except the suggested periodic replacement ofthe back-up battery 33, FIG. 8).

Additionally, as opposed to conventional controllers that generallywater for an entire season based on a single setting, the “FROGalgorithm” (the mathematical application of the FROG integration)provides an incremental adjustment based on the actual day of the yearor on a few days surrounding the watering day by using the ETo_localcharacteristic curve for the location. A conventional controller set inApril for an April to June season will deliver more water than is neededin April and/or less water than is needed in June. The FROG controller10, once initially set (or reset) with the customized waterbudget/schedule 105 (FIG. 15) determined by the FROG algorithm, willdeliver water corresponding to the local watering needs incrementallyadjusted in correlation with the watering day.

Also, in contrast to conventional controllers, consideration is given tothe number of mandated and optionally voluntary no-watering days by theFROG algorithm, so the plants receive adequate water even when thenumber of allowed watering days is greatly reduced. The novel FROGalgorithm additionally incorporates a compensation coefficient S and awatering depth factor W to further refine the total volume of waterdelivered. (The water volume is not a flow meter-measured volume, but isa quantity related to the flow rate, run-time duration, number of starttimes, number of days watered.)

The FROG integration may be advantageously used with a number of typesand configurations of irrigation control systems. Five exemplaryembodiments (with additional aspects and variations) utilizing the FROGintegration are demonstrated to illustrate the general usability of theFROG integration and algorithm with these and other configurations.

Embodiments Overview

The first embodiment of FIG. 1A, FIG. 1B presents the FROG controller asan add-on controller for connection to an existing conventionalirrigation controller 20. FIG. 1 includes a graphic display, while aneconomical, simplified user interface without a graphic display ispresented in FIG. 1B. Learn mode FIG. 12, 14 methods are presented,allowing the add-on FROG controller 10 to learn the start times andrun-time durations for the various zones of the existing controller 20.

The second embodiment of FIG. 2 presents the FROG as a comprehensivestandalone controller applying the FROG integration and/or FROGalgorithm to the watering schedule as in the first embodiment, butadditionally configured to allow a user to manually input the necessaryportion of the property-specific data (such as program start times,watering days, and run-time durations for the various zones), therebyremoving the need for the conventional controller 20.

The third embodiment of FIG. 3, FIG. 4, and FIG. 9 presents either theadd-on or the standalone FROG controller in communication with one ormore environmental sensors 41, 42.

The fourth embodiment (FIG. 5A, FIG. 5B, FIG. 5C, FIG. 5D, FIG. 6A, FIG.6B, FIG. 6C, FIG. 7A, FIG. 7B, and FIG. 7C) presents an optional datainput system 70 for use with either the add-on or standalone FROGcontroller; variations of the data input system are also presented.

The fifth preferred embodiment (FIG. 13, FIG. 14, FIG. 15, FIG. 16)presents both the data storage unit input method (with the data inputsystem using an SD card for input) and the wireless input method(utilizing a standard wireless network transmission system). The datastorage unit input method and the wireless input mode may each be usedalone or in combination.

The FROG irrigation controller 10 is targeted toward only a fewgeographical locations at a time, and, preferably, just one, such as theLas Vegas Valley. It may be programmed for only the one designatedgeographic location in which it will be used, with only the ETo_localand mandated watering restrictions (such as no-watering days and/orno-watering hours of the day and/or the watering days corresponding toeach assigned watering group and the like) of that designated geographiclocation loaded. (The term “loaded” refers to storing data, such asregulation data, evapotranspiration data, property-specific data, and/ora customized water budget/schedule 105 (FIG. 15) on a storage medium 26of the FROG irrigation controller 10, such as by the manufacturer,distributor or intermediary before installation, or when the installeror homeowner uses the data input system 70, or when the wireless system150, FIG. 14, provides the data to be stored.) If only loaded with onedesignated geographic location, the designated geographic location isnot selectable by the user and complexity is reduced. Optionally, it maybe loaded with the ETo local and mandated watering restrictions ofmultiple geographic locations, with the geographic location to bedesignated by the installer or user (such as by the use of the basic,manual control devices or data input system 70).

First Embodiment—Add-On Controller

Referring now to the first embodiment of FIG. 1, an add-on FROGcontroller 10 is designed to work with an installed existing controller20 that has been user-programmed to take into account the appropriatewatering needs of the plant types predominating in each individualirrigation zone of the user's landscape. For example, a zone comprisingpredominately turf may deploy sprayers scheduled to run on several daysat several times per day for relatively long run-time durations; a zonecomprising predominately trees and shrubs may deploy bubblers and dripemitters scheduled to run on fewer days at fewer times per day forrelatively short run-time durations. Further, zones that are relativelyshaded may be scheduled for start times and run-time durationsreflecting a different and lower watering need due to the shadedconditions.

The add-on FROG controller 10 is in communication with existingirrigation controller 20, connected to the existing controller 20 bybridge cable 12. The add-on FROG controller 10 can use the learn mode toreceive the property-specific data, as described in FIG. 12. When usingthe learn mode to input the property-specific data, the existingcontroller 20 may optimally be programmed to provide the full amount ofwater needed for each zone under the hottest and driest anticipatedconditions of the year. This is because, in this embodiment, the FROGwill cut back water output as determined by the FROG integration and/orFROG algorithm based on ETo local and watering restrictions, but doesnot boost water output beyond what has been programmed into the existingcontroller 20.

Add-On FROG Controller Components and Wiring

As shown in FIG. 8, the “main control unit” 24 of the add-on FROGcontroller 10 is enclosed in housing 48 and is wired to the existingcontroller 20, with the FROG controller 10 preferably in physicalproximity to the existing controller 20 to minimize the amount of bridgecable 12 required. Housing 48 may be designed for indoor use or maycomprise an all-weather enclosure to enable close physical proximity tothe existing controller 20, even if the existing controller 20 is in anexterior location.

The main control unit 24 comprises several groups of features,including: (1) an existing-controller input system configured to allowmain control unit 24 to communicate with the existing controller, suchas an input terminal strip 13, connecting to the AC/DC opto-couplerinput sensing circuits 14, connecting in turn to a microcontroller 22;(2) at least one non-volatile memory, storage medium 26, such as EEPROM(Electronically Erasable Programmable Read-Only Memory), and real-timeclock 25; (3) microcontroller 22 and associated circuitry; and (4) amicrocontroller water-valve regulation system configured to allow themicrocontroller to control the water control valves 30, such as byconnecting the microcontroller outputs to a zone relay bank 27,connecting to the output terminal strip 28, which is in turn wired toexisting zone cable 29 regulating water control valves 30.

Before undertaking to wire the main control unit 24 of the add-on FROGcontroller 10 to the existing controller 20, the user preferably marksor makes note of the existing controller's zone cable 29 wiring scheme,e.g., red wire connects Zone 2; black wire connects Common (C); etc. Thecable is then removed. The bridge cable 12 of the main control unit 24is then connected to the existing controller 20, as annotated, which isto say that Zone 1 of the main control unit is connected to Zone 1 ofthe existing controller 20; the Common of the main control unit isconnected to the Common of the existing controller 20; etc. To theextent the main control unit 24 has more available zone wires than theexisting controller 20 has active zones, such extra zone wires areignored and may be terminated.

Next, the main control unit 24 is connected to the irrigation valves 30by reconnecting the existing zone cable 29 to the main control unit zoneoutput terminals 28, taking care to correlate the zone and Commondesignations marked or noted during the removal process as explainedabove.

In an aspect, the main control unit 24 has its own power supply 11 (FIG.1, FIG. 8, which may include a plug-in transformer), and is separatelyplugged into an electrical outlet. By not drawing power from theexisting controller 20 as provided in prior art devices, the FROGcontroller 10 does not risk causing the existing controller 20 to exceedits power supply power rating. Optionally, though, in someconfigurations, the FROG controller 10 may draw power from an existingcontroller 20.

The FROG controller's processing power may be supplied by a conventionalmicrocontroller or microprocessor (the “microcontroller”) 22 (such as aRISC-based microcontroller based on the Harvard architecture or othermicrocontroller means currently available or as may be developed in thefuture) in conjunction with a real-time clock (the “RTC”) 25 and atleast one non-volatile memory, storage medium 26, for storing staticdata (such as EEPROM, RAM, or other memory storage means currentlyavailable or as may be developed in the future). The microcontroller 22may be preprogrammed with a supervisory program that manages allcomponents, circuits, program logic, inputs, outputs, and control (the“microcontroller program”), but at least the microcontroller 22 ispreprogrammed with a kernel program to provide minimal functionalitysufficient to receive the full “microcontroller program.” Themicrocontroller program is responsible for monitoring, managing andcontrolling the overall operation of the FROG.

The main control unit 24 may be outfitted with one or more manualcontrol devices 15, 16, 17, 18, 19, 31, 32 (such as a rotary switch,push button, or digital control), which may be indicated by an indicatordevice 65 (such as an LED, or other means, audible and/or visual). Amanual control device 15, 16, 17, 18, 19, 31, 32 can be used to inputdata or initiate events, digitally or mechanically. One or more of themanual control devices can be used to input data or to make selectionsand interface with the graphic display screen 60. For example, inresponse to displayed outputs on the display screen 60, the user caninput the applicable watering group 31 (FIG. 8) as assigned by the localwater authority, to adjust the float day 32, to initiate learn mode 17,to initiate run mode 16, or to override 18 the FROG controller. Once theinput is received, it may be stored in the storage medium 26.

In one aspect, illustrated in FIG. 1B, a simple FROG controller withouta graphic display is presented. Four manual control devices areillustrated, a learn mode input 17, a run mode input 16, a mandatedwatering group (as assigned by the local water authority) designationinput 31, and a float day input 32.

In another aspect, illustrated in FIG. 1A, the FROG controller 10 isconfigured with a graphic display 60 viewable to the user and operableto display useful information, such as displaying requests for specificuser input, values input by the user, and error messages. Optionally,the graphic display screen 60 may be a touch screen allowing directmanual control through touching the screen to make presented selections.

Add-On FROG Controller—Learn Mode

As shown in the flowchart of FIG. 12, to continue setup of the add-onFROG controller after connection of the wiring, the user activates 81the device to “learn mode.” This may be accomplished by engaging “learnmode” input 17 (FIG. 1, FIG. 8). Once learn mode is initiated, themicrocontroller program retrieves 82 the current date and time from theRTC 25. The microcontroller program then surveys 83 the number of zoneswired to the existing controller 20 by sensing the presence of polarizedvoltage levels via the AC/DC opto-couplers input sensing circuits 14(FIG. 8). Using this information, the microcontroller program dimensions84 the watering table array. Once completed, the microcontroller programpolls 85 for zone activity equating to start times and run-timedurations. It accomplishes this, for example, by using an AC/DCopto-coupler input sensing circuit 14 to sense zone activity through DCvoltage level transitions and/or alternating voltage level transitionsat a standard frequency, such as 50 Hz, 60 Hz, 120 Hz, etc. In thisfirst learn mode method, the learn mode extends over a default period oftwo weeks. Those skilled in the art will know that other default periodsmay be used, however, two weeks corresponds to the most typical defaultperiod in that homeowners using “skip-day” programs run through theirentire irrigation cycle over a two-week period. The data collected inlearn mode may be stored 86 in storage medium 26.

Depending upon the pre-determined default period, the RTC 25 maygenerate an interrupt to terminate 87 the learn mode that is passed tothe microcontroller 22, which is interpreted by the microcontrollerprogram as a termination of learn mode. Alternatively, themicrocontroller program may store the ending date and time as an endingsentinel for a matched value-type termination routine. At this time, themicrocontroller program preferably generates 88 a visual or audibleindication, such as a flashing LED 66 (FIG. 8), that learn mode iscomplete. Reacting to this, the user may activate 89 run mode, such asby pressing a run mode input button 16, or the microcontroller programmay be programmed to automatically initiate 90 run mode 80, whicheffectively transfers watering schedule control to the FROG controller.

Another aspect of the invention, in which the learn mode may be afour-week process, is presented to accommodate the installation of theFROG controller 10 at times of the year other than during the summer(since in summer the maximum water volume is already appropriate). Forexample, if the FROG controller 10 is to be installed in mid-winter whenthe water requirement for the landscape is minimal, a great deal ofwater is wasted if the summer maximum schedule is applied daily for twoweeks in order to allow the FROG controller 10 to learn the summermaximum schedule.

During the first two weeks of the four-week learn mode, the existingcontroller 20 is not adjusted to the summer maximum watering schedule,but continues on its existing, preset schedule. The FROG controller 10,in a learning-override mode, learns this “starting-point existingschedule” during the course of the first two weeks, but does not controlthe water control valves. At the end of the first two weeks, theexisting controller 20 needs to be reset by the user to the summermaximum water start times and run-time durations for all of the zones.Therefore, at the end of the first two weeks, an audio or visualreminder may be produced by the FROG controller 10, or in addition orinstead, an outside reminder input (such as a reminder letter, email,text or phone call from the water authority) may remind the homeowner ofthe need to reset the existing controller 20 to the summer maximumwatering schedule.

Though the FROG controller 10 learns the start times of the summermaximum watering schedule and may be programmed to duplicate them,optionally the FROG controller 10 may be programmed to automaticallyshift the start times toward the middle of the day during colder months.Generally the summer watering hours may be restricted by the waterauthority to the morning hours, such as before 10 a.m., to minimizeevaporation. Start times forced into the early morning may not beoptimum for colder months. The FROG controller 10 can be preloaded(Block 7, FIG. 14) with any mandated no-watering hours, as well asmandated no-watering days. Optionally, the mandated regulations can beinput into the FROG controller via the data input system 70 [Block 8,FIG. 14] or wireless system [Block 9, FIG. 14]. The FROG algorithm cangive consideration to the mandated no-watering hours and to the climateof the local geographic area and adjust the start times, as needed.

In the second two-week period of the four-week learn mode, the FROGcontroller 10, in a learning-controlling mode, enforces thestarting-point existing schedule by controlling the water control valves30, as learned during the first two-week period. Additionally, over thesecond two week period the FROG controller 10 learns the newly setsummer maximum watering schedule and stores this summer maximum wateringschedule in storage medium 26. The landscape receives the same amount ofwater in the second two-week period (as controlled by the FROGcontroller 10) as it received during the first two-week period. In thisway, without overwatering by using the summer maximum watering scheduleduring the fall, spring or winter, the FROG controller 10 can learn andstore the summer maximum watering schedule for use in the FROGintegration and/or FROG algorithm. At the end of the four-week learnmode, run mode is activated in the FROG controller 10, as describedabove (either by manual control device 16 (FIG. 12) of the user or, morepreferably, by automatic initiation 90 by the microcontroller program).

In an optional aspect, the learn mode may be implemented as alearn-while-managing method. In the learn-while-managing method thehomeowner installs the FROG controller 10 and immediately sets theexisting controller for the peak summer maximum watering schedule. TheFROG controller 10 is set to overrule the existing controller anddisallow watering for a time period of at least 24 hours (any portion ofthe first day remaining plus at least one full watering day). Duringthis overruling time period, the FROG controller 10 learns at least 24hours of the homeowner-set peak summer watering schedule. For example,if the FROG controller 10 is installed on Monday, but the first wateringday set for the summer peak schedule is Wednesday, the FROG woulddisallow the watering schedule programmed for Wednesday while learningthe single day. The FROG controller 10 will then use a temporarylearn-while-managing FROG algorithm applying the evapotranspiration data120 (FIG. 14) to only the one day of watering data from Wednesday. Onthe next day, Thursday, it controls the water valves to dispense thattemporary water budget. While implementing the temporary water budgetand schedule on Thursday, the FROG controller 10 will continue todisallow the existing controller's programmed schedule for Thursday (ifany), but will learn it. So the water is only delayed one day. If theexisting controller's summer maximum schedule is not set for Thursday,the FROG controller 10 will still apply the temporary water budget, butwill necessarily wait until the next set watering day to learn thesecond day's data. At the end of the second watering day, the FROGcontroller 10 will have learned the summer maximum watering schedule fortwo watering days, so will apply the temporary learn-while-managing FROGalgorithm to the data available, and so on and so forth, until a fullweek or, optionally, two weeks is learned. At that time, the entiresummer peak watering schedule has been learned, so thereafter run modeis activated and the FROG controller 10 will use the standard FROGalgorithm 100 (FIG. 15) to produce the customized water budget andschedule. Advantageously, this learn-while-managing method negates theneed for the homeowner to return to the FROG controller 10 at the end ofthe learning time.

Run Mode

Once in run mode, the microcontroller program first determines the dayof the week by accessing the RTC 25. If it is a no-watering day basedupon loaded regulation data or a voluntary watering restriction, thenthe FROG controller does not activate any water control valves 30throughout that day.

If it is not a no-watering day, the microcontroller program uses thecurrent date from the RTC 25 to determine the current season of theyear. Using this information, the microcontroller program applies theFROG algorithm to determine a “FROG watering budget” for the nextirrigation cycle (an amount of water comprising the optimal wateringbudget for the next irrigation cycle). Optionally, as in the fifthembodiment, the microcontroller program may simply implement thecustomized water budget/schedule 105 derived by the FROG algorithm usingthe online wizard.

Whether calculated by the FROG algorithm within the FROG controller orby the FROG algorithm using the online wizard, the determination of thisFROG watering budget and FROG schedule (start times, run durations, daysto water for each zone) to implement the water budget is made by usingthe ETo local value corresponding to the ETo value of the particular day(or an average of a set of values corresponding to nearby days) from theETo characteristic curve table of values for the designated geographiclocation, such as depicted in FIG. 10. This FROG water budget andschedule, comprising a modified and/or compensated run-time duration,may be stored in storage medium 26. The microcontroller program thenactivates the relay 27 that, in turn, activates the applicable watercontrol valve 30.

Comparison to Conventional Controllers

This is in contrast to many prior art add-on smart controllers that donot themselves control water control valves but actively monitor theexisting controller outputs and interrupt the controller, typically overthe Common wire, to modify irrigation run-time durations. The prior artarrangement effectively doubles the risk of unreliability because, whilethe FROG controller only risks disrupting irrigation if it malfunctionsitself, prior art smart controllers risk disrupting irrigation if eitherthey malfunction themselves or the existing controller malfunctionsitself

Also, as opposed to the smart irrigation controllers of the prior art,the FROG controller 10 enforces mandatory watering restrictions,provides incremental water adjustments, and provides a water budgetsufficient for the property's landscaping (when using the learn mode thewater budget is based on the total water volume at the summer peakwatering settings of the existing controller 20 delivered over a timeperiod, such as a week or since the last watering day), taking intoconsideration the number of no-watering days and calculatingcompensation coefficients along with delivery frequency adjustments.

Prior art smart controllers are merely programmed to reduce this dailywatering volume by applying an evapotranspiration rate (or by one of avariety of means), without considering the additional reduction thatwill occur as days are removed by mandated watering restrictions. Forexample, the summer maximum watering schedule is applied every day forseven days in the summer when all days are watering days. Then, inmid-winter, these controllers cut back the daily summer maximum wateringvolume, appropriately resulting in a significant reduction in water tobe delivered on a daily basis (a “winter reduced daily volume”).However, prior art smart controllers do not take into account the largenumber of no-watering days that may be mandated by local waterauthorities. Consequently, the “winter reduced daily volume” is, infact, not applied daily, resulting in an over-reduction in waterdelivery. For instance, in the Las Vegas Valley, only one watering dayis allowed in winter—consequently six days are no-watering days. If thisis not taken into consideration, the water delivered to the homeowner'sproperty is a mere fraction of the needed amount determined bylandscaping needs: only one of the winter reduced daily volume amountsis delivered on the one available day.

Exemplary FROG Algorithm Applying FROG Integration

In one exemplary aspect of the FROG algorithm, the microcontrollerprogram of the FROG controller 10 may use the FROG algorithm tocalculate the initial total volume of water delivered by the existingcontroller during a particular time period (a particular number of daysnear the day of watering, such as the week before watering, as used inthe below example, Mo_(x/wk), FIG. 11). This total volume (Mo_(x/wk)) isproportionally distributed (with other factors taken into account) tothe number of allowed watering days near the day of watering, such as aweekly cycle. This total volume of water (Mo_(x/wk)) may be used in thedetermination of the scaled watering minutes for each watering event foreach zone (Mo_(x/event), FIG. 11). The FROG algorithm may also be usedby the FROG system to assist in calculating the customized FROG waterbudget and watering schedule 105 (FIG. 15), a schedule based on theinitial watering schedule of the existing controller 20 but modified bythe FROG integration of mandated watering restrictions and theempirically-derived evapotranspiration local characteristic curve and/orother factors, as herein presented.

Two refining factors, a watering depth factor W and a compensationcoefficient S may be used to further refine the optimal watering budget.

The watering depth factor W provides a reduction in water delivery,reflecting a reduced watering requirement due to the increased wateringdepth provided when utilizing the customized water budget and schedule105 (FIG. 15) provided by the FROG algorithm. As promoted by the localwater authorities, the FROG controller 10 delivers a proportionallylarger volume of water that is applied at less frequent intervals.Consequently, the water penetrates the soil more deeply, less surfaceevaporation occurs, and more water is left in the soil for the plant toaccess. Additionally, the less frequent, deeper watering provided byusing the FROG algorithm encourages deeper root growth in plants,resulting in healthier plants.

The compensation coefficient S is used to further refine the FROGalgorithm of the present invention. The compensation coefficient S is afactor correcting for lack of daily watering frequency due to mandatedno-watering restriction days, the corresponding plant seasonal moistureneeds, and an assumed soil type characteristic of the locale (affectingthe water delivery rate [percolation] calculations).

Referring to FIG. 11, the FROG algorithm used by the FROG controller 10,includes the following variables:

D_(x/wk)=Initial number of Days per week that Zone_(x) valve is open(91, FIG. 11).

E_(x/day)=Initial number of watering Events per day for Zone valve (92,FIG. 11).

Mo_(x/event)=Minutes of initial run-time duration (initial minutes perwatering event for Zone_(x) from existing controller settings) (93, FIG.11).

Mo_(x/wk)=initial watering Minutes of water per week for Zone_(x) (fromexisting controller settings) (96, FIG. 11).

Ms_(x/event)=Scaled watering Minutes (run-time duration) of water perevent for Zone_(x) (96, FIG. 11).

D_(A/wk)=number of Days Allowed per week considering mandated 135, FIG.14 and voluntary 190, FIG. 14 watering restrictions (94, FIG. 11), witha minimum value of 1. This is preloaded (Block 7, FIG. 14) in the firstembodiment, but in the fifth embodiment may also be input through thedata input system 70 (Block 8, Block 23, FIG. 14) or through thewireless system 150 (Block 9, Block 24, FIG. 14).

ETo_local=value for Day_(n) from ET local characteristic curve (95, FIG.11). This is preloaded (Block 4, FIG. 14) in the first embodiment, butmay also be input via the data input system 70 [Block 5, Block 20, FIG.14] or wireless system [Block 6, Block 21, FIG. 14] before distributionof the FROG controller 10 or by the user at a later time.

ET_(ave)=average of the ETo_local values of the days since last watering(98, FIG. 11).

W=Watering Depth factor allowing reduction of the total volume of waterdue to the reduction in water need due to the increased depth ofwatering resulting from a larger volume of water applied at largerintervals.

S=Compensation coefficient, a factor correcting for lack of dailywatering frequency due to no-watering restriction days (mandated orvoluntary), the corresponding plant seasonal moisture needs, and anassumed soil type characteristic of the locale (affecting the waterdelivery rate [percolation] calculations).

As seen in FIG. 11, the variables D_(x/wk), E_(x/day), and Mo_(x/event)are determined from the learn mode in the first embodiment. The D_(A/wk)and ETo_local may be pre-loaded (Block 7, Block 22, Block 4, Block 19,FIG. 14) or input via the data input system 70 [Block 8, Block 23, Block5, Block 20, FIG. 14] or wireless system [Block 9, Block 24, Block 6,Block 21, FIG. 14] into the FROG controller 10. And Mo_(x/wk) andMS_(x/event) are calculated in the following equation:Mo _(x/wk)=(D _(x/wk))*(E _(x/day))*(Mo _(x/event))

For example (for a single zone x, summer maximum set at existingcontroller):

5 min/event*3 events/day*7 days/week=105 minutes/week

The Ms_(x/wk) derived from UN-AVERAGED ETo_local value (using theETo_local value of the particular date) is derived from the followingequation:(Mo _(x/wk) /[D _(A/wk) *E _(x/day)])*(ETo local)*S*W=Ms _(x/wk)

A somewhat more refined Ms_(x/wk) may be obtained by averaging multipleETo_local values (averaging the ETo_local values of the days since lastwatering or another set of ETo_local values from nearby days).

First ET_(ave) is calculated by averaging the ETo_local valuescorresponding to the days since the last watering; then ET_(ave) issubstituted in the above equation resulting in the following equation:(Mo _(x/wk) /[D _(A/wk) * E _(x/day)])*(ET _(ave))*S*W=Ms _(x/wk)

So, in the above example, 105 minutes/week divided by 3 days per week(allowed by watering restrictions) times 3 events per day (the number ofwatering events per day programmed in the existing controller)=11.66minutes/event multiplied by the Compensation coefficient S and theWatering Depth Factor W and the scale factor ETo_local (in theun-averaged equation) or ET_(ave) (in the averaged equation).

Many modifications may be made to the above equations to provide furtherbenefits or to achieve conservation goals. For example, though theexample variables are based on a time period of a week, other timeperiods are equally usable, such as a two-week period. Or, for anotherexample, the algorithm can be simplified, such as by omitting the Scoefficient or the W factor.

Also, optionally, instead of using E_(x/day) to determine Ms_(x/wk),(where E_(x/day) represents the number of watering events per day forZone_(x) of the summer watering schedule), it may be desirable to use areduced number of watering events per day (for instance in winter whenwatering is minimized). Thus, a winter algorithm might use E_(W/day)(where E_(W/day) represents the number of watering events per day forZone_(x) preferred in the winter season):(Mo _(x/wk) /[D _(A/wk) *E _(W/day)])*(ET _(ave))*S*W=Ms _(x/wk)

Another modification may be made to the above exemplary equations toaccount for the voluntary no-watering day discussed below. If thevoluntary no-watering day is enabled, the D_(A/wk) (the number of daysallowed per week as defined in the mandated watering restriction) wouldbe reduced by 1 (the one voluntary no-watering day) unless that wouldresult in zero watering days. Therefore, the minimum for D_(A/wk) is oneday, as the minimum number of watering days a week is one day.

The usefulness and/or novelty of the algorithm combines with theusefulness and/or novelty of the integration of the mandated no-wateringdays and the empirically-derived evapotranspiration local characteristiccurve, with the possibility of further integrating the voluntaryno-watering day, and in the availability of the presented variables,factors, and coefficients for manipulation to derive a FROG wateringschedule that achieves the goals of adequate water delivery for thelandscape and of water conservation.

Once the foregoing process is complete, the microcontroller programawaits the next start time, whereupon the process may be repeated, andso on and so forth until the entire irrigation cycle is complete. Whenthe entire irrigation cycle is complete, the entire process repeats atthe next scheduled irrigation cycle, and may continue to do so until anerror occurs or the user intervenes to stop the cycle. There is noinherent need for the user to reprogram or interact with the FROG at theonset of a new season as previously required for conventional irrigationcontrollers.

Override Mode

In an aspect, the FROG controller may have a bypass or “override mode”permitting the user to operate his existing controller manually asthough there were no FROG in series between the existing controller 20and the irrigation valves 30. Preferably, the FROG is configured withmanual input device 18 to activate override mode, along with an audibleor visual indicator device 67, such as a flashing LED, to signal thatoverride mode is running. For aesthetics, the input device 18 andindicator 67 preferably coordinate in appearance and location the othermanual control devices 15, 16, 17, 19 and indicators 66, 65 of learnmode and run mode. When the user has activated override mode, themicrocontroller program performs all functions as usual, except thatinstead of causing “on” and “off” commands to be communicated to therelays 27 operating the irrigation valves 30, it simply causes the “on”and “off” commands of the existing controller 20 to be communicated tothe relays 27 operating the irrigation valves 30.

At times, the user may forget to activate the override mode. Variousaccommodations may be made to deal with this situation. For example, theuser may have just planted a new plant in a particular zone and,consequently, may decide to manually run the particular zone for anexceptional watering. If the FROG controller 10 immediately “learns” theone-time run of the particular zone, the watering budget and schedulemay be updated based on the one-time run. However, this may not be thecase. Rather, it may be the case that the user wishes to alter theexisting watering schedule of the particular zone on a permanent basisand, therefore, makes a change to the run time of the zone. If the FROGcontroller 10 does not “learn” the change, the plants will not receivethe changed amount of water on an ongoing basis. Therefore, preferably,the FROG controller 10 is configured to hold any newly changed settingsuntil a particular grace time period has passed (such as midnight of theday of the change, ten or twelve hours from the change, etc.). Anindicator (visual, auditory, or both) and/or on-screen message can say,“Is this a temporary change?” If the user does not respond within thegrace period, the change is considered to be an intended setting change.Thus, this additional time gives the user a grace period wherein he canremember to cancel the change if it is a one-time change instead of anintended setting change.

Another exemplary method may be used to ascertain whether the userintends to alter the existing watering schedule of the particular zoneon a permanent basis, or to perform a one-time exceptional watering, bycausing the FROG controller 10 to refuse to implement the water commanduntil the user designates his choice. The FROG controller 10 willrespond to the user's attempt to manually intervene without selecting“bypass” by warning the homeowner to switch to bypass if a permanentchange is not intended. This reminder occurs by means of a visual and/oraudible signal, but more importantly (since the user is interacting withhis existing controller, not the FROG controller 10), by not activatingthe valve(s) unless and until the user either switches to bypass mode onthe FROG controller 10 or indicating, on the FROG controller 10, that hedesires the change to be permanent. Disabling the activation of thevalve(s) compels the user to designate a choice in ways the audible orvisual signal may not.

When the FROG controller is in the four-week learn mode, during thefirst two weeks the microcontroller program operates the FROG controlleras though it were in override mode for purposes of irrigation. However,operation in override mode is not indicated by the override modeindicator and, unlike override mode, the FROG controller 10 surveys thewired zones, etc., as provided above.

Second Embodiment—Manual Property-Specific Data Input

The second embodiment, shown in FIG. 2, of the FROG 10 is acomprehensive, standalone controller, which also utilizes the FROGintegration of the present invention, but additionally is configuredwith all the functionality of a conventional irrigation controller,allowing a user to manually input property-specific data (watering days,start times, run-time durations for the various zones). There is nolonger a need for the existing controller 20 or another conventionalcontroller. The user should manually input the property-specific datarepresenting the water budget and schedule for the middle of the summerfor use in the FROG algorithm. The FROG algorithm then uses theproperty-specific data that has been manually input as a substitute forthe property-specific data learned in the first embodiment, andcalculates the water budget and schedule for the current day of theyear.

In the second embodiment, conventional rotary dials 57, switches, anddigital input devices allow the user to manually program the FROGcomprehensive, standalone controller 10. The standalone controller 10may be housed in an open housing 48 (FIG. 4) or in a housing with a door58 (FIG. 2, FIG. 13). If installed in an inside location, a conduit 59may be connected to the housing to allow the field wires to be routed tothe outside water control valves 30.

Third Embodiment—Sensor Input

The third embodiment of FIG. 3, FIG. 4, and FIG. 9 also utilizes theFROG integration and/or FROG algorithm of the present invention, butfurther includes at least one local or remote environmental sensor 41,42 operable to measure environmental conditions, such as temperature,humidity, solar radiation, soil moisture, rainfall, or the like, as areknown, or may become known, in the art. The local sensor may be disposedwithin or adjacent to the housing 48, 58 and may be directly orwirelessly connected to the main control unit 24.

With the remote sensor, a sensor module 60 may be included that isconnectable to either the add-on FROG (FIG. 3) or the standalone FROG(FIG. 4). The sensor module 60 is operable to communicate with a remoteweather station 55 (FIG. 3, FIG. 4, FIG. 9). Preferably, theenvironmental sensors 41, 42 are configured to communicate wirelesslywith the main control unit 24, which is configured to receive andprocess the received remote sensor data. The remote weather station 55includes one or more operable environmental sensors 41, 42 (FIG. 9).Optionally, the sensor receiver may be located within the housing 48,58, instead of in a connectable module.

The addition of one or more environment sensors 41, 42 to providecurrent environmental data may, in some cases, provide a beneficialrefinement to the FROG integration and/or FROG algorithm of the presentinvention. Additionally, some municipalities mandate the usage of one ormore sensors with any installed automatic irrigation controller (such asa mandated rain gauge). Thus, the FROG controller 10 of the thirdembodiment is adapted to meet that requirement.

The remote, freestanding weather station 55 is preferably mounted in anexterior location where accurate environmental readings can be obtained.Preferably the sensor data are wirelessly transmitted by a transmissiondevice, such as RF transmitter 43 (with antenna 38), to obviate the needfor wiring. Therefore, the weather station 55 is preferably situated ina suitable location to allow wireless communication through walls madeof ordinary construction materials. The FROG controller 10 is configuredwith a corresponding RF receiver 39 (FIG. 8).

Optionally, the sensors 41, 42, as well as the RF transmitter 43, may bepowered by a solar-powered system, comprising a solar energy conversionpanel 45, solar charger 47, and a charge storage system 46. Use of sucha solar-powered system eliminates the expense, maintenance and disposalof batteries, plus avoids the inevitable disruption caused by undetectedbattery failure.

In one exemplary aspect, the sensors 41, 42 output their readings tomodulation device 44 that is set to turn on the RF transmitter 43 andrelay readings at a predetermined sample rate, such as once per hour,continuously day and night. The sample rate is sufficient to provideaccurate overall environmental values, expressed as an arithmeticaverage, over the entire time period from one irrigation cycle to thenext, but not so frequent as to unnecessarily draw down system resourcesand interfere with the similar systems operating at adjacent properties.

To use the sensor data, the sensor data are preferably averaged and thevalues stored in storage medium 26. On watering days, themicrocontroller program retrieves the current group of environmentalsensor readings in storage medium 26 for the specific time period ofinterest, preferably, since the last scheduled start time for the zonein question. The microcontroller program uses an environmental-factorcalculation algorithm to output a current temperature value and currenthumidity value. The environmental-factor calculation algorithmpreferably calculates the arithmetic average of readings from the time agiven irrigation cycle was last scheduled to the time it is nextscheduled to derive a “current environmental factor.” Other similarenvironmental-factor calculation algorithms (such as ones that excludeoutliers or average only the last two days) are also within the scope ofthe invention.

The current environmental factor E, may be used as an additional scalingfactor in the FROG algorithm, as follows:(M _(ox/wk) /[D _(A/wk) *E _(x/day)])*(ETo_local)*S*W*E=M _(sx/wk)Fourth Embodiment—Data Input System 70

The fourth embodiment (FIG. 5A, FIG. 5B, FIG. 5C, FIG. 5D, FIG. 6A, FIG.6B, FIG. 6C, FIG. 7A, FIG. 7B, FIG. 7C) presents an optional data inputsystem 70 for use with either the add-on or standalone FROG controller10, either with or without one or more environmental sensors. The datainput system 70 allows a user (or water authority representative) toconveniently input information into the FROG controller 10, thus, theFROG controller 10 can be updated periodically, either frequently orinfrequently, as needed.

Data Input System—Optical (Fourth Embodiment)

In a first aspect, FIG. 5A, FIG. 5B, FIG. 5C, FIG. 5D, the data inputsystem 70 includes a data input receiver embodied as an optical codereader 72 within a reader slot 71 configured to receive an insertablesheet 68 imprinted with an optical code 69.

The optical code 69 may be a printed QR Code®, bar code, matrix code, orother two-dimensional code for carrying data. The optical code 69 maycontain any of a variety of water restriction information or irrigationcontroller instructional information; this information is individuallycustomizable for the particular home (or business). For example, opticalcode 69 may be used to specify the mandated watering restrictions, tospecify the assigned watering group, to specify the geographic location,to change the start times, or the like. Moreover, the optical code 69allows the water authority to implement changes to data loaded into theFROG controller 10, the necessity of which may become greater as theyears pass. For instance, if weather and climate patterns change (suchas through changes in the La Niña and El Niño patterns, global warming,or the like), the loaded empirically-derived evapotranspiration localcharacteristic curve may become less reliable. It is easy to update theFROG controller 10 using the optical code 69 (or other disclosed datainput system 70); thus the FROG controller 10 will continue to performwithin a reasonable range of conservation expectations, with theparameter values at or near current climatic conditions.

The optical code 69 is printed on the insertable sheet 68 in anappropriate location to position the optical code 69 for reading whenthe insertable sheet 68 is inserted into the reader slot 71.

The optical code reader 72 captures the visual information from theoptical code 69 and converts it into a corresponding digital code usableby the microcontroller.

The availability of a simple means to allow the user to input data maybe of great advantage to both the user and to the water authority. Forinstance, the local water authority can (at virtually no cost) routinelyprint an optical code 69 carrying the mandated watering restrictions,geographic location, the assigned watering group, and/or an updatedempirically-derived evapotranspiration local characteristic curve forthe home associated with the bill. If the FROG controller 10 experiencesa power outage without the backup battery power, one or more settingsmay be lost or corrupted (including the loaded mandated wateringrestrictions and/or geographic location and/or assigned watering group).The homeowner merely inserts the bill with the optical code 69 into thereader slot 71, and the optical reader 72 converts the optical data tore-establish the mandated watering restrictions and/or geographiclocation and/or assigned watering group and/or other settings.Instructions on how to insert the bill so that the optical code 69 isreadable can also be printed on the bill. As no interaction is requiredwith the local water authority employees, this method of re-establishingdata is very cost effective for the water authority, as well as beingconvenient for the homeowner.

Additionally, if the homeowner receives digital bills instead of paperbills, the homeowner can log onto his account at the water authority andprint the optical code 69 customized for his home, which is theninserted into reader slot 71.

Further, easy instructions can be presented by using the optical code69. For example, if the real-time clock needs to be reset, the homeownercan log onto his account online and print an optical code 69, which,when inserted into reader slot 71, causes easy, step-by-stepinstructions for resetting the clock to be displayed on the graphicdisplay 60.

An insertable sheet 68 carrying optical code 69 could optionally beincluded with a new FROG controller 10, to initially establish somevariables.

Data Input System—Magnetic (Fourth Embodiment)

In a second aspect of the fourth embodiment, FIG. 6A, FIG. 6B, FIG. 6C,the data input system 70 includes a data input receiver embodied as amagnetic code/smartcard reader 74 configured with a slide track or slideslot 73 configured to receive a data-carrying card 77 (such as a plasticcard with an embedded magnetic code using magnetic stripe technology ora smartcard having an embedded microprocessor with stored data or thelike). The FROG controller 10 is configured with the slide track 73, themagnetic code/smartcard reader 74, and corresponding circuitry.

The card 77 carrying data 78 may be similar to a credit card in size.Data-carrying card 77 can be supplied to the homeowner upon request ormight optionally be included with a new FROG controller 10. The magneticcode/smartcard reader 74 is adapted for reading the carried data 78.

In a similar manner as in the first aspect, the carried data 78 cancontain any data or information needed by the homeowner, such asmandated watering restrictions, geographic location, assigned wateringgroup, etc.

Data Input System—Data Storage Unit (Fourth Embodiment)

In a third aspect of the fourth embodiment, FIG. 7A, FIG. 7B, FIG. 7C,the data input system 70 is shown as receiving data input via anon-volatile memory storage device. The FROG controller 10 is configuredto receive data stored in a data storage unit 79. The FROG controller 10is configured with a data input receiver embodied as a magneticcode/smartcard reader 74 with an electronic interface 75 configured toreceive a complementary electronic connector 61 of the data storage unit79. The electronic interface 75 may be an industry standard connection(such as a USB interface, an SD card interface, or other conventionalnon-volatile data storage device interface) allowing communication to beestablished between the external data storage unit 79 and the FROGcontroller 10. The microcontroller is configured to read the digitallystored data on the data storage unit 79.

As illustrated, a data storage unit 79, such as a flash drive or othernon-volatile memory card, can be configured with complementaryelectronic connector 61. Optionally, a computer having scheduling and/orirrigation software could interface with the FROG controller 10 via theelectronic interface 75 to facilitate remote control, to allow dynamicscheduling capabilities, and/or to input the customized waterbudget/schedule 105.

The data input system 70 of the third aspect functions similarly to thedata input systems 70 of the first and second aspects and can containdata for establishing data, re-establishing data, inputting thecustomized water budget/schedule 105, and/or providing instructionalinformation. Additionally, sufficient data can be conveyed to the FROGcontroller 10 to update the microcontroller program.

Fifth Embodiment—Data Storage Unit and Wireless

FIG. 13 illustrates the preferred fifth embodiment of the presentinvention, and shows a preferred type of the data input system 70 inwhich the FROG receives data via a data input receiver embodied as an SDcard reader having an electronic interface 75 complementary to an SDcard interface 61. The data storage unit 79 is an SD card 79A configuredwith the complementary electronic connector 61 which is inserted intothe SD card slot 75A. Though illustrated as a Secure Digital (SD) memorycard, other non-volatile memory cards (such as SDHC, SDXC, SDIO,miniSDHC, microSDHC, Memory Stick, Compact Flash, MMC, or other formatsof data storage units containing non-volatile storage memory, as knownin the art or become known in the future, preferably that can beelectrically erased and reprogrammed) are within the scope of theinvention.

The preferred fifth embodiment of FIG. 13 may be located in an indoorlocation (such as a garage) or in an outdoor location. To facilitateplacement in the outdoor location, to provide storage for instructions,and for aesthetic reasons, the FROG controller is configured with a door58 connected by hinges 54 to the main housing of the FROG controller 10.The door 58 may also have a door locking mechanism 53A that isconfigured to engage with the complementary housing locking mechanism53B. Preferably the door 58 is also configured with a door pocket 56,allowing the homeowner to store instructional materials, notes, or thelike in a convenient location. Preferably, to provide further weatherresistance, the manual control devices 15, 16, 17, 18, 19 and indicatordevice 65 (shown as an indicator light) may be recessed within a cavity52. Labeling 33 is preferably used to assist the user in installing andupdating the FROG controller 10. The housing 58 is preferably formed ofa material having a surface that will readily accept labeling 33.

Means Of Inputting Data Into The FROG System (FIG. 14)

As shown in FIG. 14, the FROG controller 10 of the fifth embodiment maybe configured as any of the following: (1) an add-on FROG controller 10Acontrolling the water valves, but used with an existing controller; (2)a standalone FROG controller 10B controlling the water valves without anadditional controller; or (3) a converted FROG controller 10C in whichthe controller is used first as an add-on controller, but at the time ofinstallation has the potential and functionality included to beconverted to a standalone controller at a later time.

A converted FROG controller 10C might be advantageous to allow a waterauthority to encourage initial early installation of the controllerfunctioning as an add-on FROG controller 10A. Then, as resources areallocated and time permits, an additional system, such as the data inputsystem 70 or wireless system 150 can be implemented, with the convertedFROG controller 10C then able to function as a standalone FROGcontroller 10B.

As illustrated in FIG. 14 in Block 1, the add-on FROG controller 10A canobtain property-specific data 110 by using the learn mode 140. Aspresented in the first embodiment of FIG. 1A and FIG. 1B, the add-onFROG controller 10A may have only the learn mode 140 available to obtainproperty-specific data 110. However, in the preferred fifth embodiment,optionally, by use of the customization wizard (FIG. 15) to create acustomized water budget/schedule 105 the property-specific data 110 canbe input through data input mode 70 functionality (Block 2) and/orwireless input mode 150 functionality (Block 3) can be included. Thisallows the FROG controller to be transformed into a converted FROGcontroller 10C, removing the necessity for an additional controller,existing controller 20.

As shown in Blocks 4 to 6, the add-on FROG controller 10A may obtain theevapotranspiration data 120 by having it preloaded 160 into the memorystorage medium 26 of the system before distribution to the homeowner, byusing the data input mode 70, and/or by using the wireless input mode150.

As shown in Blocks 7 to 9, the add-on FROG controller 10A may obtain themandated 135 portion of the regulation data 130 by having it preloaded160 into the system before distribution to the homeowner, by using thedata input mode 70, and/or by using the wireless input mode 150.

As shown in Blocks 10 to 12, the user may input his choice of avoluntary no-watering day (voluntary no-watering data 190) by manualinput 165 into the system, by use of the customization wizard to createa customized water budget/schedule 105 that is input by using the datainput mode 70, and/or by using the wireless input mode 150.

As shown in Block 13, the customized water budget/schedule 105 may beobtained by the add-on FROG controller 10A by calculating 155 it basedon the FROG algorithm 100 as described above.

As shown in Blocks 14 to 15, the customized water budget/schedule 105may be obtained by the add-on FROG controller 10A through use of theweb-based wizard (FIG. 15), then by using the data input mode 70 and/orby using the wireless input mode 150.

As shown in Block 16, the standalone FROG controller 10B can obtainproperty-specific data 110 by manual 165 manipulation of physical dials,buttons, and controls, as in the second embodiment of FIG. 2.

As shown in Blocks 17 to 18, by use of the customization wizard tocreate a customized water budget/schedule 105, the standalone FROGcontroller 10B receives property-specific data 110 by using the datainput mode 70 functionality and/or wireless input mode 150functionality.

As shown in Blocks 19 to 21, the standalone FROG controller 10B mayobtain the evapotranspiration data 120 by having it preloaded 160 intothe system before distribution to the homeowner, by using the data inputmode 70, and/or by using the wireless input mode 150.

As shown in Blocks 22 to 24, the standalone FROG controller 10B mayobtain the mandated data 135 by having it preloaded 160 into the systembefore distribution to the homeowner, by using the data input mode 70,and/or by using the wireless input mode 150.

As shown in Blocks 25 to 27, the user may input his choice of avoluntary no-watering day (voluntary no-watering data 190) by manualinput 165 into the FROG controller 10. Optionally, by using thecustomization wizard to create a customized water budget/schedule 105the voluntary restriction can be input into the system by using the datainput mode 70, and/or by using the wireless input mode 150.

As shown in Blocks 28 to 29, the customized water budget/schedule 105may be obtained by the standalone FROG controller 10B through use of theweb-based wizard (FIG. 15) then by using the data input mode 70 and/orby using the wireless input mode 150. The data input mode 70 may be usedeither by the user or by the distributor of the FROG controller. Forexample, the user can create the customized water budget/schedule 105for his FROG controller by use of the web-based wizard, and then thedistributor can easily input the customized water budget/schedule 105into the user's FROG controller by using the convenient data input mode70 (such as by inserting an SD card to initialize the FROG controller),before the user takes possession of his FROG controller 10B.

Example-Add-On

Any combination of these modes may be used. For example, a convertibleFROG controller 10C (FIG. 4) may be issued to a user. The FROGcontroller 10C could first function as an add-on controller, but wouldhave the unrevealed functionality included to be optionally converted toa standalone controller (for example, at a later time when time andresources allow the water authority to provide the necessarycorresponding functionality, such as a website wizard or wireless inputsystem). When initially functioning as the add-on FROG controller, itmay be preloaded 160 (Block 4) by the distributor by inserting a datastorage unit carrying evapotranspiration data 120 and mandated data 135into a data storage unit receiver, then may execute the learn mode 140(Block 1) to acquire the property-specific data 120 with the customizedwater budget/schedule 105 then calculated 155 (Block 13). If the onlinecustomization wizard is available and the user decides to designate oneday a voluntary no-watering day, he can use the web-based wizard (FIG.15) to obtain a new customized water budget/schedule 105; a new SD card79A (FIG. 13) is mailed to the user, who then inserts it into the SDcard slot 75A, thereby using the data input mode 70 (Block 11, Block 23)to update his FROG controller 10, without further calculations needed.At a later date, the ETo characteristic curve for the geographic areamay need adaptation for climate change; if the wireless network systemis available, the wireless input mode 150 (Block 14) may be used toupdate the FROG controller 10 without user input.

Web-Based Customization Wizard

FIG. 15 shows steps in using the web-based wizard to create a customizedwater budget/schedule 105. The customization wizard may typically bepresented by the local water authority (or an authorized provider). Thecustomization wizard provides convenient access for the user to utilizethe FROG algorithm 100 to create a personal, customized waterbudget/schedule 105 that can then be input into the user's FROGcontroller 10. As discussed in relation to FIG. 14, the water budget andschedule 105 may be input through preloading 160 of the system beforedistribution, by using a data storage unit 79 (such as an SD card, usingthe data input system 70), or by wireless transmission 150.

To access the configuration and customization wizard, the user browses111 to the website presenting the customization wizard and registersand/or logs in 112. The first time the user accesses the customizationwizard, registration is preferably required to associate a user name andpassword with a particular property address receiving water from thelocal water authority. On later visits, the user will preferably onlyneed to log in to the website to use the customization wizard.

The customization wizard allows the user to input any of a variety ofproperty-specific data 110, such as the number of zones or valves 113,the plant type 114 (turf, shrubs, trees, low-water-use native shrubs,etc.) for each of the valves, and the plant environment 115 for theplants in each zone (shade, part sun, full sun, flat, incline, steepincline, sandy soil, loam, etc.). Optionally, the user may walk abouthis property with an Internet-enabled mobile phone to assist indetermining property-specific data 110, using the Internet to access thewizard and directly input information. Also, optionally, a map image,such as a GOOGLE EARTH® image may be included within the wizard toassist in inputting property-specific data 110.

The evapotranspiration data 120 (ETo characteristic curve for thegeographic area) and the mandated data 135 (permitted watering hours andmandatory no-watering days) are stored in a database accessible by theFROG algorithm 100 and associated with addresses within the area to beserved.

Upon input of the property-specific data 110 by the user, the FROGalgorithm accesses the evapotranspiration data 120 and the regulationdata 130 corresponding to the address of the property, and creates acustomized water budget/schedule 105. So, by merely following thestraightforward on-screen instructions, the user can input theproperty-specific data needed to allow the FROG algorithm 100 to createthe customized water budget/schedule 105 that provides sufficient waterfor the landscaping, while implementing the water restrictionregulations. As shown in FIG. 14, the customized water budget/schedule105 can be delivered to the FROG controller 10 via the data input system70 or the wireless transmission mode 150. The data input system 70 maybe used to input the customized water budget/schedule 105 by thedistributor before distribution or by the user. For example, thecustomized water budget/schedule 105 can be placed on an SD card; the SDcard with the customized water budget/schedule 105 can be mailed to theuser, the user can pick it up at the water district, etc. Alternatively,the user may download the customized water budget/schedule 105 onto hiscomputer and install it onto an SD card or download it directly to an SDcard, which can be inserted into the SD card reader.

Wireless Transmission Mode

FIG. 16 illustrates an example of the wireless transmission mode 150 inwhich a data input receiver is embodied as a wireless data receiver thatcan be used to input the same types of data into the FROG controller 10as the data input system 70, described above. These data include, asshown in FIG. 14, the initial or updated customized waterbudget/schedule 105, property-specific data 110, evapotranspiration data120, and regulation data 130 (mandated restrictions 135 and voluntarywater restrictions 190). The wireless transmission mode 150 isconfigured to provide a wireless transmission between the local waterauthority (or its representative) and the FROG irrigation controller 10of each homeowner.

Any of a variety of wireless connection methods as are known, or becomeknown in the art can be used to transmit the customized waterbudget/schedule 105 to the FROG controller 10 through the use ofInternet connectivity, radio-frequency (RF) transmission, cellular phonetransmission, or other transmission systems using a standardizedcommunication protocol. Preferably the wireless connection mode chosenis secure and scalable, while allowing the individual FROG controllers10 to use a transmission component having a small size, low cost, andlow power consumption.

Advantageously, the wireless transmission mode 150 may fulfill the datainput function for the FROG controller without the expense of adedicated wireless system, as the water authority may already have inplace (or have in development) a wireless system for reading itssubscribers' water meters. Thus, if water authority vehicles are rovingneighborhoods to read meters wirelessly or if the water authority has awireless network set up to read meters remotely, the wirelesstransmission mode 150 may be piggybacked onto the water authorityexisting wireless system. The water authority wireless system can thenefficiently perform two functions at the same time, reading the metersand re-setting FROG controllers 10.

Though other wireless systems are usable, FIG. 16 presents a preferredRF mesh network and transmission components based on the IEEE 802.15.4standard. An exemplary type of mesh wireless network is currentlyavailable using components meeting the ZigBee specification developed bythe ZigBee Alliance, which is based on the IEEE 802.15.4 standard andspecifies operation in the 2.4 GHz, 915 MHz, and 868 MHz ISM RF bands.

Each FROG controller 10 is configured as a node (10-1, 10-2, 10-3, 10-n)on the network. Each FROG controller 10 includes an operative ZigBee endnode component, a reduced functionality device (RFD) having a wirelesstransceiver with an antenna configured to receive and transmit data overthe air, but configured for low-power usage and long battery life. TheRFDs can wirelessly communicate with a ZigBee router 121-1, 121-2, 121-nor ZigBee coordinator 125. The ZigBee router 121-1, 121-2, 121-n canalso wirelessly communicate with a ZigBee coordinator 125. A meshnetwork web server 123 may be provided to allow configuration andcontrol of the network. The web server 123 may be directly connected orwirelessly connected to the ZigBee coordinator 125. The mesh network webserver 123 may additionally also provide the online customizationwizard, but preferably the mesh network web server 123 is connected to asecond customer-accessible web server that provides the customizationwizard. Methods of secure communication provided in the ZigBeespecification are preferably used.

Additionally, the end node 10-n can be accessed directly by a user ortechnician without use of the mesh network, including without accessingthe web server 123, the coordinator 125, or the router 121-1. The endnode 10-n is provided with functionality allowing it to be accessed viaa direct wireless connection to a corresponding connectable computer fordiagnostic or local control connectivity, as described in the ZigBeestandard.

To use the wireless system, the customized water budget/schedule 105that was created by the homeowner using the online wizard is transmittedto the mesh network web server 123 from the customization web server (ifseparate from the mesh network web server 123). The mesh network webserver 123 transmits the customized water budget/schedule 105 in packetsto the coordinator 125 that wirelessly transmits the customized waterbudget/schedule 105 to the mesh network, which are received by theindividual homeowner's FROG controller 10. The packet transmission maytake any of many available routes. The ZigBee specification provides forbest effort multi-hop transmission, which is used to provide efficientwireless transmission.

Voluntary No Water “Float” Day

In another aspect of the FROG smart controller of the present invention,the ability for the homeowner to choose to designate one additional dayas a user-donated “float” day (a voluntary no-watering day) is enabled.Preferably the homeowner not only specifies that he wishes to relinquishone allowed watering day, but also may be allowed to choose theparticular day of the week to be relinquished. This is generally done inexchange for a credit from the local water authority on the homeowner'swater bill. Thus, an advantage is provided to both the local waterauthority (reduction in water usage) and to the homeowner (reduction inwater bill).

One problem occurs if the float day is able to be enabled by thehomeowner via a manual input device or the data input mode 70 (Block 14,Block 23, FIG. 14)—the local water authority cannot be assured that theremotely located FROG controller 10 in the individual's house hasremained enabled. The homeowner could remove the float day activation,yet still receive the bill credit. To prevent this problem, the FROGcontroller 10 may be sold in two species, a float-day-enabled FROGcontroller 10 and a no-float FROG controller 10. The float-day-enabledFROG controller 10 may be homeowner configured either manually or by thedata input mode 70. If configured manually, a user-option toggle ispreferably included and is operable to manually or digitally allow thehomeowner to change the day of the week of the float day, but not tomanually remove the enabled float day. If the float-day enabled FROGcontroller 10 is to be configured by data input, the homeownerpreferably configures or reconfigures his customized waterbudget/schedule 105 using the web-based wizard to change the day of theweek, which the homeowner then inputs into his FROG controller 10 viathe data input mode 70 (Block 14, Block 23, FIG. 14).

Removal of the float day (if, for example, the homeowner later changeshis mind) could be implemented by sending a water authority serviceperson to manually change the setting, but is preferably implementedwithout the use of water authority employee time. The float day can beremoved by use of the data input mode 70, but cannot be re-enabled againby the data input mode 70B. The homeowner can access the web-basedwizard to create a new customized water budget/schedule 105 removing thecredit and the float day. A new SD card 79A can be mailed to thehomeowner or picked up by the homeowner from the water authority. If thehomeowner then inserts the new SD card 79A into the SD card slot 75A toupdate his FROG controller 10, the microcontroller program is instructedto remove the float day. If the homeowner fails to insert the new SDcard 79A to update his FROG controller 10, he continues to donate thefloat day, but no longer receives the credit on his bill. However, thefloat day cannot be re-enabled through the data input mode 70, as thewater authority cannot be assured the new SD card 79A has been insertedto update the FROG controller 10 and activate a float day, so cannotprovide a water credit.

Preferably, however, the float day may be enabled and disabled by usageof the wireless input mode 150 (Block 15, Block 24, FIG. 14). Using thewireless input mode 150 would remove the need for two types of FROGcontrollers, as the water authority would be assured that thehomeowner's customized water budget/schedule 105 (activating, changing,or removing the float day) was input wirelessly into the homeowner'sFROG controller 10. The usage of the wireless input mode 150 would alsoallow multiple enabling and disabling of the float day on anindividual's FROG controller 10.

Additionally, removal of the float day would be equally simple. Thehomeowner can access the web-based wizard to create a new customizedwater budget/schedule 105. The updated customized water budget/schedule105 can be automatically transmitted wirelessly 150 to the homeowner'sFROG controller. Upon removal of the voluntary no-watering float day,the homeowner would no longer receive a water credit.

From the foregoing, it will be apparent that the FROG smart controller10 solves the problem of delivering adequate water for landscaping needsby utilizing the empirically-derived evapotranspiration localcharacteristic curve and local mandatory and voluntary wateringrestrictions, while incorporating a water need increase affected by thereduced number of mandated and voluntary no-watering days and a waterneed reduction affected by deeper, less frequent watering.

Since many modifications, variations, and changes in detail can be madeto the described preferred embodiments of the invention, it is intendedthat all matters in the foregoing description and shown in theaccompanying drawings be interpreted as illustrative and not in alimiting sense. Thus, the scope of the invention should be determined bythe appended claims and their legal equivalents.

We claim:
 1. An irrigation controller for regulating at least one watercontrol valve corresponding to a watering zone, comprising: anirrigation controller comprising: a housing; a microcontroller housedwithin said housing and programmed with a microcontroller program thatreceives data; a data input system configured to allow data to beimported into said irrigation controller; wherein said data input systemcomprises a data input receiver operable to receive a customizedwatering budget/schedule; at least one non-volatile memory storagemedium configured to receive and to store data from saidmicrocontroller; and a real-time clock operatively connected to saidmicrocontroller; a customer-accessible processor providing an irrigationcustomization software application; wherein said customer-accessibleprocessor performs the steps of: (1.) receiving input property-specificdata; (2.) accessing evapotranspiration data for at least one locality;(3.) accessing any mandatory watering restriction regulation data; and (4.) calculating said customized watering budget/schedule for at leastone designated watering zone for distribution over a specified timeperiod based on using a minute-based representation of a total watervolume and by allocating said total water volume or allocating a reducedtotal water volume to be distributed within said specified time periodfor said designated watering zone; wherein said customized wateringbudget/schedule is based on at least said input property-specific data,on said evapotranspiration data, and on said any regulation data;wherein said customized watering budget/schedule allocates saidminute-based representation of a total water volume into a particularnumber of watering days per said specified time period for saiddesignated watering zone, into a particular number of watering eventsper each of said watering days for said designated watering zone, andinto a particular number of minutes per said watering event for saiddesignated watering zone; wherein said microcontroller is electricallyconnected to said at least one water control valve associated with saiddesignated watering zone; and wherein said microcontroller electricallyopens and closes said at least one water control valves based on saidcustomized watering budget/schedule for said designated zone.
 2. Theirrigation controller for regulating at least one water control valvecorresponding to a watering zone, as recited in claim 1, wherein saiddata input receiver comprises a wireless receiver.
 3. The irrigationcontroller for regulating at least one water control valve correspondingto a watering zone, as recited in claim 1, wherein said data inputreceiver comprises a data storage unit.
 4. The irrigation controller forregulating at least one water control valve corresponding to a wateringzone, as recited in claim 1, further comprising an environmental sensorthat senses at least one environmental factor and outputs sensor data;wherein said microcontroller program receives said sensor data andrevises said customized watering budget/schedule.
 5. The irrigationcontroller for regulating at least one water control valve correspondingto a watering zone, recited in claim 4, wherein said data input receivercomprises a data storage unit.
 6. The irrigation controller forregulating at least one water control valve corresponding to a wateringzone, as recited in claim 1, wherein: said irrigation controller allowsinput of a user-selectable voluntary no-watering day restriction; andsaid microcontroller program receives said input of said user-selectablevoluntary no-watering day restriction; said microcontroller programrevises said customized watering budget/schedule received through saiddata input system based on said input of said user-selectable voluntaryno-watering day restriction; and said microcontroller program prohibitswatering on said voluntary no-watering day on an ongoing basis.
 7. Theirrigation controller for regulating at least one water control valvecorresponding to a watering zone, as recited in claim 1, wherein: saidinput property-specific data includes at least one initial start timefor said designated watering zone; said customer-accessible processorshifts said at least one initial start time for said designated wateringzone to create an alternate zone start time that differs from said atleast one initial start time.
 8. The irrigation controller forregulating at least one water control valve corresponding to a wateringzone, as recited in claim 1, wherein said representation of said totalwater volume comprises a representation of the peak summer maximumwatering volume.
 9. The irrigation controller for regulating at leastone water control valve corresponding to a watering zone, as recited inclaim 8, wherein: said customized watering budget/schedule is calculatedfor said specified time period by determining the current day andmultiplying an evapotranspiration factor, from said evapotranspirationdata, associated with said current day or multiplying an average ofevapotranspiration factors, from said evapotranspiration data,associated with a small range of days including said current day by saidrepresentation of said total water volume for said specified timeperiod.
 10. The irrigation controller for regulating at least one watercontrol valve corresponding to a watering zone, as recited in claim 8,wherein said customized watering budget/schedule is calculated for saidspecified time period by determining the current day and reducing saidrepresentation of said total water volume for said specified time periodby a factor determined from said evapotranspiration data associated withsaid current day or with an average of said evapotranspiration dataassociated with a small range of days including said current day. 11.The irrigation controller for regulating at least one water controlvalve corresponding to a watering zone, as recited in claim 1, whereinsaid customized watering budget/schedule for said specified time periodis calculated by dividing said representation of said total water volumefor said specified time period by a number of allowed or desiredwatering days per said specified time period.
 12. The irrigationcontroller for regulating at least one water control valve correspondingto a watering zone, as recited in claim 1, wherein: said representationof said total water volume for said specified time period is reduced bya watering depth factor; and said watering depth factor is based on areduction in water need due to increased depth of watering.
 13. Theirrigation controller for regulating at least one water control valvecorresponding to a watering zone, as recited claim 1, whereincustomer-accessible processor is accessed through an Internet website.14. The irrigation controller for regulating at least one water controlvalve corresponding to a watering zone, as recited in claim 1 whereinsaid minute-based representation of a total water volume to bedistributed within said specified time period for said designatedwatering zone is determined by multiplying a number of initial days persaid specified time period for said designated watering zone times anumber of initial watering events per said specified time period forsaid designated watering zone times a number of minutes of initial valverun-time duration for said designated watering zone.